Method and System for Family Plan Sharing of Wireless Services

ABSTRACT

A system and process of sharing a wireless surface allotment in a third party wireless network includes implementing a metering system to meter wireless service usage by users of the third party wireless network and tracking wireless usage by a plurality of wireless devices associated with the metering system. The system and process further includes receiving a share request to reallocate the respective wireless service allotment for at least two of the plurality of wireless devices, forwarding modification instructions to the metering system, requesting confirmation from the metering system that the modification instructions have been received, and modifying the respective wireless service allotments for the at least two wireless devices in response to receiving confirmation from the metering system.

CROSS REFERENCE TO PRIOR APPLICATIONS

This application is a continuation of the U.S. patent application Ser.No. 15/702,995, filed Sep. 13, 2017, now U.S. patent Ser. No. 10/021,546issued Jul. 10, 2018, which is incorporated herein by reference in itsentirety; which is a continuation of the U.S. patent application Ser.No. 15/049,318, filed Feb. 22, 2016, now U.S. Pat. No. 9,769,642 issuedSep. 19, 2017, which is incorporated herein by reference in itsentirety. This application also claims the benefit from U.S. ProvisionalApplication No. 62/118,738 filed on Feb. 20, 2015, which is herebyincorporated by reference for all purposes as if fully set forth herein.

BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure

This disclosure relates generally to a process and system forimplementing shared wireless service between two or more wireless users.

2. Related Art

Certain companies that provide wireless services, such as mobile phoneservice, can be wireless carriers or Mobile Network Operators (MNOs)that maintain, operate, and control their own wireless networks andtypically have control of their own frequency spectrum. An MNO reliesheavily on backend systems to address any provisional, billing,security, and data issues that might threaten the health of theirnetworks.

MNOs use the backend system to provide shared wireless services. Forexample, current mobile shared plans include wireless service plans thatallow subscribers to access a shared source of data or minutes and areallocated to the wireless user on a first-come first-serve basis.Alternatively, there exists shared wireless plans where a single user isallocated all the wireless services, i.e. parent device, and theservices are allocated to wireless devices part of the shared plan, i.e.children devices.

A Mobile Virtual Network Operator (MVNO) is a mobile operator thattypically does not own its own frequency spectrum and typically does nothave its own network infrastructure. Instead, MVNOs have businessarrangements and contracts with third party wireless carriers topurchase usage of their networks (e.g., minutes of voice calls, volumeof data transfer, number of SMS, service days, etc.) that the MVNOs inturn sell to their own customers.

MVNOs utilize a number of different ways to meter wireless services totheir customers including handset based metering, hybrid metering, andserver based metering. In handset based metering of wireless services,the handset implements a secure model for metering, charging, andmaintaining the wireless services. The handset maintains a softwarealgorithm that typically meters the cellular subscriber's usage, and hassome level of back-end control for provisioning and adding airtime tothe line.

Hybrid metering utilizes a combination of the handset based metering anda server associated with the MNO in order for the MVNO to provideoversight for metering, charging, monitoring, and maintaining thewireless services. Server based metering relies on tracking informationfrom the MNO in order for the MVNO to provide oversight for metering,charging, monitoring, and maintaining the wireless services. However,the handset based metering, hybrid metering, and server meteringutilized by MVNOs is based on allocation of wireless service on a perwireless user basis (and for a predetermined time period) and this doesnot provide an effective approach to share various wireless servicesbetween two or more wireless users.

Accordingly, there is a need for a Mobile Virtual Network Operator(MVNO) to be able to allow two or more wireless users on individualwireless plans to share wireless service.

SUMMARY OF THE DISCLOSURE

The foregoing needs are met, to a great extent, by the disclosure, witha process and system for implementing wireless services that are sharedbetween two or more wireless devices.

In one or more aspects, then process of sharing a wireless surfaceallotment in a third party wireless network, includes implementing ametering system to meter wireless service usage by users of the thirdparty wireless network, tracking wireless usage by a plurality ofwireless devices associated with the metering system, receiving a sharerequest to reallocate the respective wireless service allotment for atleast two of the plurality of wireless devices, forwarding modificationinstructions to the metering system, requesting confirmation from themetering system that the modification instructions have been received,and modifying the respective wireless service allotments based on anexchange rate for the at least two of the plurality of wireless devicesin response to receiving confirmation from the metering system.

In another aspect, a wireless network provider system configured toshare a wireless service allotment of a plurality of wireless devices ina third party wireless network includes a metering system configured tomeasure usage of wireless services of the third party wireless networkby the plurality of wireless devices, the metering system being furtherconfigured to receive a share request to reallocate the respective usageallotment for at least two of the plurality of wireless devices, and themetering system being further configured to modify the respective usageallotments based on exchange rate for the at least two of the pluralityof wireless devices in response to receiving confirmation from the atleast two of the plurality of wireless devices.

There has thus been outlined, rather broadly, certain aspects of thedisclosure in order that the detailed description thereof may be betterunderstood herein, and in order that the present contribution to the artmay be better appreciated. There are, of course, additional aspects ofthe disclosure that will be described below and which will form thesubject matter of the claims appended hereto.

In this respect, before explaining at least one aspect of the disclosurein detail, it is to be understood that the disclosure is not limited inits application to the details of construction and to the arrangementsof the components set forth in the following description or illustratedin the drawings. The disclosure is capable of aspects in addition tothose described and of being practiced and carried out in various ways.Also, it is to be understood that the phraseology and terminologyemployed herein, as well as the abstract, are for the purpose ofdescription and should not be regarded as limiting.

As such, those skilled in the art will appreciate that the conceptionupon which this disclosure is based may readily be utilized as a basisfor the designing of other structures, methods, and systems for carryingout the several purposes of the disclosure. It is important, therefore,that the claims be regarded as including such equivalent constructionsinsofar as they do not depart from the spirit and scope of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a mobile network, a wireless device, and a mobile virtualnetwork operator in accordance with aspects of the disclosure.

FIG. 2 shows tracking component processes in accordance with aspects ofthe disclosure.

FIG. 3 shows a sharing process in accordance with aspects of thedisclosure.

FIG. 4 shows the details of a wireless device in accordance with aspectsof the disclosure.

DETAILED DESCRIPTION

Reference in this specification to a “wireless device” is intended toencompass any compatible mobile technology computing device thatconnects to a wireless communication network, such as mobile phones,mobile equipment, mobile hotspots, wearable devices, mobile stations,user equipment, cellular phones, smartphones, handsets or the like(e.g., APPLE® IPHONE®, IPAD®, GOOGLE® ANDROID® based devices,BLACKBERRY® based devices, other types of PDAs or smartphones), wirelessdongles, or other mobile computing devices. The term “wireless device”may be interchangeably used and referred to herein as “wirelesshandset,” “handset,” “mobile device,” “device,” “mobile phones,” “mobileequipment,” “mobile station,” “user equipment,” “cellular phone,”“smartphones,” “mobile hotspots,” “wearable devices,” or “phone.” Theterm, “service plan” is intended to encompass any combination of voice,texts, data, and any non-data service provided to the wireless device.The terms, “shared plan,” “business plan” and “family plan” are intendedto encompass any service plan utilized by more than one device and anygrouping of service plans that are owned by an entity such as a businessentity. Further, reference in this specification to a “wireless network”or “network” is intended to encompass any type of wireless network fromwhich a MVNO contracts with a MNO wireless carrier to provide mobilephone services through the use of a wireless device, such as the GlobalSystem for Mobile Communication (GSM) network, Code-Division MultipleAccess (CDMA) network, 4G-LTE, 5G, or the like, that may utilize theteachings of the present application to allow a wireless device toconnect to a wireless network.

Reference in this specification to “one aspect,” “an aspect,” “otheraspects,” “one or more aspects” or the like means that a particularfeature, structure, or characteristic described in connection with theaspect is included in at least one aspect of the disclosure. Theappearances of, for example, the phrase “in one aspect” in variousplaces in the specification are not necessarily all referring to thesame aspect, nor are separate or alternative aspects mutually exclusiveof other aspects. Moreover, various features are described which may beexhibited by some aspects and not by others. Similarly, variousrequirements are described which may be requirements for some aspectsbut not other aspects.

The following acronyms used herein will be defined as follows:

BSC—Base Station Controller

BTS—Base Transceiver Station

CDMA—Code-Division Multiple Access

ESN—Electronic Serial Number

GSM—Global System for Mobile communication

HLR—Home Location Register

ICCID—Integrated Circuit Card Identification

IMEI—International Mobile Equipment Identity

IMSI—International Mobile Subscriber Identity

Ki—Authentication Key

LAI—Local Area Identity

LTE—Long Term Evolution

MSC—Mobile services Switching Center

MMS—Multimedia Messaging Service

MVNO—Mobile Virtual Network Operator

OTA—Over-The-Air

SMS—Short Message Service

UICC—Universal Integrated Circuit Card or SIM

UMTS—Universal Mobile Telecommunications Service

VLR—Visitor Location Register

The disclosure is a way for wireless users to share wireless serviceswith family members by transferring unused wireless services betweenwireless devices. Any wireless device can request and send data, voiceminutes, text messages, service days, or other features to othermembers. Transferring “service days,” between any family members orshared plan members can be beneficial because this can prevent usersfrom having their wireless service cut off. Furthermore, as this abilityto share wireless services may be implemented with a MVNO, the sharingcan be implemented across different carriers within a family plan.

FIG. 1 shows the details of a mobile network 102, a plurality ofwireless devices 104(1)-104(n) (where n is any whole number), and amobile virtual network operator (MVNO) cloud 152 in accordance withaspects of the disclosure. The disclosure may use a metering server 150that may reside in the MVNO cloud 152 or may be stand-alone. Themetering server 150 may be implemented as a server, computer, system,distributed processing system, cloud-based system or the like, or aplurality of the same. The MVNO cloud 152 may be implemented as anetwork, internet cloud, server, computer, system, distributedprocessing system, cloud-based system or the like. The metering server150 may be responsible for one or more of provisioning, metering, andconsolidating information for the wireless subscribers of wirelessdevices such as the wireless device 104. The metering server 150 may beconfigured to implement the further functionality as described infurther detail below.

Alternatively or additionally, the disclosure may use a metering server158 that may reside in the network 102. The metering server 158 may beimplemented as a server, computer, system, distributed processingsystem, cloud-based system or the like, or a plurality of the same. Themetering server 158 may be responsible for one or more of provisioning,metering, and consolidating information for the wireless devices such asthe wireless device 104. The metering server 158 may be configured toimplement the further functionality as described in further detailbelow.

Alternatively or additionally, the disclosure may utilize a trackingclient 154 that may be associated with the wireless device 104. Thetracking client 154 may be pre-installed or post-installed on thewireless device 104. The tracking client 154 may track usage of thewireless device 104. Moreover, the tracking client 154 may report usageinformation to the metering server 150. The tracking client 154 may beconfigured to implement the further functionality as described infurther detail below.

When sharing wireless service, the respective tracking clients154(1)-154(n) may track the usage of the corresponding wireless devices104(1)-104(n) and/or the total usage of the wireless services.Alternatively or additionally, when sharing wireless service, themetering server 158 may track the usage of the corresponding wirelessdevices 104(1)-104(n) and/or the total usage of the wireless services.Alternatively or additionally, when sharing wireless service, themetering server 150 may track the usage of the corresponding wirelessdevices 104(1)-104(n) and/or the total usage of the wireless services.

In the following description, particular example is made of the wirelessdevice 104, however, wireless devices 104(1)-104(n) may each includesome or all of the elements/functionality described with respect to thewireless device 104. In one aspect, some or all of the wireless devices104(1)-104(n) may be configured to share wireless service with some orall of the wireless devices 104(1)-104(n).

FIG. 4 shows the details of a wireless device in accordance with aspectsof the disclosure. As shown in FIG. 4, the wireless device 104 providesthe radio and signal processing needed to access a network 102 forwireless services. The wireless device 104 includes a processor 114,memory 116, display 118, transceiver 120, user interface 122, computerreadable medium 126, and the like as is known in the art. The processor114 may be configured to process call functions, provide other servicesto the user, and may also execute any programs including the trackingclient 154 if utilized in one of the particular aspects describedherein.

It should be noted that the tracking client 154 may also be stored on orexecute, at least in part, on a Subscriber Identification Module (SIM)or Universal Integrated Circuit Card (UICC) (Hereinafter genericallyreferred to as a SIM 112), on dedicated hardware includingsemiconductors, application specific integrated circuits (ASIC),programmable logic arrays, the processor 114, and other hardwaredevices. The tracking client 154 may also execute partially orcompletely on the network 102 and/or any other network including anyform of cloud computing and the like. The tracking client 154 may alsoexecute partially or completely in the MVNO cloud 152.

In arrangements that use a SIM 112, the SIM 112 may be associated withthe wireless device 104. The SIM 112 may be an integrated circuit thatstores information and/or data such as an International MobileSubscriber Identity (IMSI) and also may store a key used to identify andauthenticate subscribers on the wireless device 104 and other devices.The SIM 112 may be configured to be transferred between differentwireless devices. SIM 112 may also store network-specific informationused to authenticate and identify subscribers on the network 102.

FIG. 1 further shows that the network 102 may include a Mobile servicesSwitching Center (MSC) 106 that may perform the switching of calls andthat may include a Visitor Location Register (VLR) 124. The network 102may also include a Base Transceiver Station (BTS) 108 and a Base StationController (BSC) 110. The base transceiver station 108 houses the radiotransceivers that define a cell and handle the radio-link protocols withthe wireless device 104. The base station controller 110 manages theradio resources for one or more base transceiver stations 108. The basestation controller 110 is the connection between the wireless device 104and the Mobile service Switching Center (MSC) 106.

A Home Location Register (HLR) 156 and the VLR 124 together with the MSC106, provide the call-routing and roaming capabilities. The HLR 156contains all the administrative information of each subscriberregistered in the corresponding network 102, along with the currentlocation of the wireless device 104.

The above is an exemplary implementation of the network 102. Other typesof networks utilizing other types of protocols may be implemented aswell and are contemplated by the disclosure.

FIG. 2 shows tracking component processes in accordance with aspects ofthe disclosure. As described above, the tracking client 154, themetering server 150, and/or the metering server 150 may operate to trackwireless usage of the wireless devices 104(1)-104(n). For brevity, thetracking client 154, the metering server 150, and/or the metering server150 will be referred to hereinafter as a tracking component.

In particular, the tracking component may implement processes toidentify 302 the wireless device 104 and/or particular wirelesssubscriber; implement tracking processes 304 to track the usage of thewireless subscriber and/or wireless device 104; implement processes toreport the usage of wireless services by the wireless subscriber using areporting process 306; and implement processes to allow for sharingwireless services 308.

When two or more of the wireless devices 104(1)-104(n) are authorized toshare wireless services, each of the wireless devices 104(1)-104(n) mayinitially operate to use wireless services consistent with a prepaidamount of wireless service purchased and allocated to each of thewireless devices 104(1)-104(n). Thereafter, according to the disclosure,portions of the wireless service may be shared among the wirelessdevices 104(1)-104(n) as further described below.

In a particular aspect, the tracking component may identify 302 theparticular wireless subscriber and/or the wireless device 104 byproviding identification information of the particular wirelesssubscriber and/or the wireless device 104 as shown by the process 300 inFIG. 2. In particular, the information may include network-specificinformation as required by the network. Additionally, the trackingcomponent may provide specific information in order to provide the MVNOand/or the MVNO cloud 152 the ability to positively identify thewireless subscriber and/or wireless device 104. The network-specificinformation may include for example one or more of an Integrated CircuitCard Identification (ICCID), Electronic Serial Number (ESN),International Mobile Equipment Identity (IMEI), International MobileSubscriber Identity (IMSI), Local Area Identity (LAI), and so on. Ofcourse other types of information are within the spirit and scope of thedisclosure.

The tracking component may also execute a tracking process 304 to trackwireless usage in each of the wireless devices 104(1)-104(n). Inparticular, the tracking component may monitor the length of each voicecall, the area code and/or the phone number that is placed based on thevoice call, and the like. Additionally, the tracking component maymonitor the amount of data that is sent or received by the wirelessdevice 104. Moreover, the tracking component may monitor the number ofSMS text messages or the like that are received or sent by wirelessdevice 104. Additionally, the tracking component may monitor the numberservice days used or the like by the wireless device 104. Furthermore,any other type of usage of the wireless device 104 may be tracked forpurposes of monitoring the wireless services. Additionally, for each ofthe above noted services provided to the wireless device 104, thefurther details of what network handled the services may also betracked. Moreover, the date and time of the usage may be tracked aswell. Finally, the tracking component may also track any other aspect orusage of the wireless device 104 and accordingly these aspects arewithin the scope and spirit of the disclosure. This information or usagemetric information that is accumulated based on the tracking of theabove noted usage may then be stored in a secure location and/or storedin an encrypted manner to avoid the usage data from being compromised.

Additionally, the tracking process 304 may display the various metrics.For example, tracking process 304 may display the number of minutes ofairtime used on the display 118 of the wireless device 104. Similarly,the tracking process 304 may also display the amount of data sent andreceived. Likewise the tracking process 304 may also display the amountof text messages sent and/or received. Finally, the tracking process 304may also display the number of service days used. Moreover the trackingprocess 304 may provide a display of the amount of airtime, data,service days, and/or text messages that may be remaining from thepreviously purchased and/or credited amount of airtime, data, servicedays, and/or text messages. In other words, if a wireless user hadpurchased 100 min. of airtime and they used 70 min. of airtime, thetracking process 304 may display “30 min. of air time remaining.”Additionally or alternatively, the tracking process 304 may display thecurrent airtime, data, service days, and/or text messages used and/orremaining.

As shown in the reporting process 306, the tracking component maycommunicate the usage information to the metering server 150. Thecommunication of the usage information to the metering server 150 maytake place at predetermined times, after predetermined amounts of usage,in an ad hoc manner, or the like. For example, the tracking client 154may communicate in response to a request from the metering server 150.The tracking client 154 may communicate with the metering server 150and/or MVNO cloud 152 across one or more mediums to convey usage metricsinformation. In one or more aspects, the tracking client 154 may beconfigured to send activity reports, such as by SMS, MMS messages or thelike, to the metering server 150.

For example, the wireless device 104 may send a SMS text messageproviding the usage metric information of the wireless device 104 to themetering server 150. The wireless device 104 can also send the usagemetric information via e-mail, packet form, datagram, USSD messages orthe like. If the wireless device 104 has Wi-Fi capability, the reportingprocess 306 may wait until the wireless device 104 connects to a Wi-Fihotspot to send the information over the Internet.

In one or more aspects, a reporting SMS message may be sent with one ormore of the following pieces of information: the IMEI; the ESN, the UICCICC-ID; the length of each voice call, the total time of voice calls,the area code and/or the phone number that is placed based on the voicecall; the amount of data that is sent and received; the total number ofSMS text messages received and the total number of SMS text messagessent; and the date and time for each usage.

In one or more aspects, for such SMS reporting messages, the trackingclient 154 may be configured to possess a destination address for themessages and a detail format (e.g., as provided by the MVNO or carrier)of the messages. In one aspect, the wireless device 104 SMS fields maybe coded as a clear text ASCII comma separated value. The listing ofparameters that may be reported may be stored securely in the wirelessdevice 104 or on the SIM 112 (if utilized).

Alternatively or additionally, the metering server 158 may communicatein response to a request from the metering server 150. The meteringserver 158 may communicate with the metering server 150 and/or MVNOcloud 152 across one or more mediums to convey usage metricsinformation. In one or more aspects, the metering server 158 may beconfigured to send activity reports or the like, to the metering server150.

As shown in the sharing process 308, the wireless device 104 user maycommunicate a request to share wireless service with another wirelessdevice 104 user. The sharing process 308 may reallocate usage allotmentsof wireless services of the wireless devices 104(1)-104(n) that eachutilize their own allocated wireless service. In particular, the sharingprocess may be initiated in response to a sharing request from a user.This request may be verified as coming from the user in any suitablemanner. For example, an authentication procedure may be performed.

The sharing request may be initiated at one of the wireless devices104(1)-104(n). In this regard, a user of one of the wireless devices104(1)-104(n) may send a SMS text message to a particular addressrequesting transfer of voice minutes, data, text messages, and/orservice days to another one of the wireless devices 104(1)-104(n). Forexample, the user may send the following text: “TRANSFER 5 SERVICE DAYSTO 3055551234.” Thereafter, the sharing process 308 would transfer 5service days to the one of the wireless devices 104(1)-104(n) having thephone number 3055551234. As another example, the user may send thefollowing text: “TRANSFER 50 TEXT TO 3055551234.” Thereafter, thesharing process 308 would transfer 50 text messages to the one of thewireless devices 104(1)-104(n) having the phone number 3055551234. Asimilar process could be utilized for data and voice minutes.

The sharing request may additionally or alternatively be initiated viathe internet. In this regard, a user of one of the wireless devices104(1)-104(n) may have an account with the MVNO that is accessible viawebpage. This webpage Internet account may allow the user to login andtransfer one or more of voice minutes, data, text messages, service daysand the like to another user of one of the wireless devices104(1)-104(n).

The sharing request may additionally or alternatively be initiated via awireless device application implemented on one of the wireless devices104(1)-104(n) by a user of one of the wireless devices 104(1)-104(n).This application may allow the user to login and transfer one or more ofvoice minutes, data, text messages, service days and the like to anotheruser of one of the wireless devices 104(1)-104(n). The sharing requestmay additionally or alternatively be initiated via a service technicianacting on behalf of the user, or the like. Other approaches toinitiating a request to share wireless services are contemplated aswell.

FIG. 3 shows a sharing process in accordance with aspects of thedisclosure. The metering component may execute the sharing process 308as shown in FIG. 3. In general, this sharing process 308 is toreallocate usage allotment of the wireless devices 104(1)-104(n) thateach utilize their own allocated wireless service. In particular, thesharing process may be initiated in response to the metering componentreceiving a sharing request from a user at step 510. This request may beverified as coming from the user in any suitable manner. For example, anauthentication procedure may be performed. The request may be initiatedat one of the wireless devices 104(1)-104(n), via the internet, via aservice technician acting on behalf of the user, or the like asdescribed above.

At step 512, the usage of all relevant wireless devices 104(1)-104(n)may be determined in order to determine if there is sufficient wirelessservice available for the request to be performed. The term, “relevantwireless devices 104(1)-104(n)” is to be understood to encompass all thewireless devices 104(1)-104(n) that might be affected by the request toshare wireless service. In a particular example, with ten wirelessdevices 104-104 i, if the user of one of these device wishes to sharesome portion of their wireless service to another user, then there mayonly be two relevant wireless devices out of the ten devices. The usageof wireless service of these relevant wireless devices 104(1)-104(n) maybe determined by polling the tracking component or the respectivetracking components of these relevant wireless devices 104(1)-104(n).

At step 514, it may be determined if the request is in compliance bycomparing the share request to the wireless service allotment remainingin the relevant wireless devices 104(1)-104(n). For example, if theshare request indicates 50 minutes of call time is to be transferredfrom the wireless device 104 a to a wireless device 104 b and thewireless device 104 a has less than 50 minutes remaining, then therequest would not be in compliance and the user would be informed atstep 516 so that the user could revise the share request. If the sharerequest is determined to be in compliance, the modification instructionscan be pushed or forwarded to the relevant tracking component at step518. In various examples, the modification instruction may be sent viadata and/or non-data. Examples of non-data include SMS, premium SMS, andthe like. Of note, in some aspects, the modification instruction aloneis not sufficient to actually cause the modification to the wirelessservice allotment. In some examples, a confirmation is also sent at step520 and the modifications are not stored to the tracking component untilall confirmations have been received at step 522. It is an advantage ofthese examples that the wireless service allotment of one wirelessdevice 104(1)-104(n) cannot be increased without also decreasing thewireless service allotment of another wireless devices 104(1)-104(n).

If confirmation is not received from the tracking component, an errorprocedure may be performed at step 524. The error procedure may includeany suitable step or series of steps. In various examples, the errorprocedure may include resending the confirmation request, resending theconfirmation request a predetermined number of times before cancellingthe sharing instruction, resending the confirmation request using adifferent method (e.g., first via data, then via SMS or other non-data),informing the user of the confirmation failure and requesting theyensure the relevant wireless devices 104(1)-104(n) are powered on withsufficient reception to the network 102, and the like.

At step 526, the wireless service allotment may be modified according tothe sharing instruction. For example, in response to all theconfirmations being received, the respective tracking clients154(1)-154(n) may be updated with the modified wireless service usageallotment. In another example, the metering server 150 may execute thesharing process 308. In particular, the metering server 150 may have theability to modify the wireless service allotments for the relevantwireless devices 104(1)-104(n). The metering server 150 may modify thewireless service allotment in accordance with the sharing instruction.Thereafter, the sharing process 308 may modify any databases associatedwith respect to the usage allotment on wireless network and/or wirelessuser to ensure the correct charges for airtime, data, service days,and/or text messages are stored in the databases. In yet anotherexample, the metering server 158 may have the ability to modify thewireless service allotments for the relevant wireless devices104(1)-104(n). The metering server may modify the wireless serviceallotment in accordance with the sharing instruction. Thereafter, thesharing process 308 may modify any databases associated with respect tothe usage allotment on wireless network and/or wireless user to ensurethe correct charges for airtime, data, service days, and/or textmessages are stored in the databases. Thereafter, the sharing processends at 528.

A variation of the sharing process 308 may include a limitation on thetimes that voice minutes, data, text messages, service days and the likemay be shared. For example, the sharing process 308 may only beimplemented the last 10 days of a particular service month. Other timeframes are contemplated as well. Similarly, the sharing process 308 mayinclude a limitation on the number of times that voice minutes, data,text messages, service days and the like may be shared. Both of theselimitations would reduce the likelihood of the system being overutilized.

A further variation of the sharing process 308 may include the abilityfor the user to share voice minutes, data, text messages, service daysand the like within their own device. In other words, allow a user tocarry over voice minutes, data, text messages, service days and the liketo the next month through the sharing process 308.

A further variation of the sharing process 308 may include the abilityto provide for a conversion rate when sharing voice minutes, data, textmessages, service days and the like. In other words, if a user shares Xtext messages with another user, the cost will be Y text messages. WithY being greater than X.

A further variation of the sharing process 308 may include the abilityto provide for a conversion to sharing voice minutes, data, textmessages, service days and the like to another type of wireless service.In other words, if a user shares Z text messages with another user, thecost will be W voice minutes.

Accordingly, the disclosure is a way for wireless users to sharewireless services with family members by transferring them betweenwireless devices. Any wireless device can request and send data, voiceminutes, text messages, service days or other features to other members.

For the purposes of this disclosure a computer readable medium storescomputer data, which data can include computer program code that isexecutable by a processor of the SIM or mobile device, in machinereadable form. By way of example, and not limitation, a computerreadable medium may comprise computer readable storage media, fortangible or fixed storage of data, or communication media for transientinterpretation of code-containing signals. Computer readable storagemedia, as used herein, refers to physical or tangible storage (asopposed to signals) and includes without limitation volatile andnon-volatile, removable and nonremovable storage media implemented inany method or technology for the tangible storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer readable storage media includes, but is not limitedto, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memorytechnology, optical storage media, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any otherphysical or material medium which can be used to tangibly store thedesired information or data or instructions and which can be accessed bya processor or computing device. In one or more aspects, the actionsand/or events of a method, algorithm or module may reside as one or anycombination or set of codes and/or instructions on a computer readablemedium or machine readable medium, which may be incorporated into acomputer program product.

In an aspect, the disclosure may be web-based. For example, a server mayoperate a web application to allow the disclosure to operate inconjunction with a database. The web application may be hosted in abrowser-controlled environment (e.g., a Java applet and/or the like),coded in a browser-supported language (e.g., JavaScript combined with abrowser-rendered markup language (e.g., Hyper Text Markup Language(HTML) and/or the like)) and/or the like such that any computer runninga common web browser (e.g., Internet Explorer™, Firefox™, Chrome™′Safari™ or the like) may render the application executable. A web-basedservice may be more beneficial due to the ubiquity of web browsers andthe convenience of using a web browser as a client (i.e., thin client).Further, with inherent support for cross-platform compatibility, the webapplication may be maintained and updated without distributing andinstalling software on each.

Aspects of the disclosure may include a server executing an instance ofan application or software configured to accept requests from a clientand giving responses accordingly. The server may run on any computerincluding dedicated computers. The computer may include at least oneprocessing element, typically a central processing unit (CPU), and someform of memory. The processing element may carry out arithmetic andlogic operations, and a sequencing and control unit may change the orderof operations in response to stored information. The server may includeperipheral devices that may allow information to be retrieved from anexternal source, and the result of operations saved and retrieved. Theserver may operate within a client-server architecture. The server mayperform some tasks on behalf of clients. The clients may connect to theserver through the network on a communication channel as defined herein.The server may use memory with error detection and correction, redundantdisks, redundant power supplies and so on.

Aspects of the disclosure may include communication channels that may beany type of wired or wireless electronic communications network, suchas, e.g., a wired/wireless local area network (LAN), a wired/wirelesspersonal area network (PAN), a wired/wireless home area network (HAN), awired/wireless wide area network (WAN), a campus network, a metropolitannetwork, an enterprise private network, a virtual private network (VPN),an internetwork, a backbone network (BBN), a global area network (GAN),the Internet, an intranet, an extranet, an overlay network, Near fieldcommunication (NFC), a cellular telephone network, a PersonalCommunications Service (PCS), using known protocols such as the GlobalSystem for Mobile Communications (GSM), CDMA (Code-Division MultipleAccess), GSM/EDGE and UMTS/HSPA network technologies, Long TermEvolution (LTE), 5G (5th generation mobile networks or 5th generationwireless systems), WiMAX, HSPA+, W-CDMA (Wideband Code-Division MultipleAccess), CDMA2000 (also known as C2K or IMT Multi-Carrier (IMT-MC)),Wireless Fidelity (Wi-Fi), Bluetooth, and/or the like, and/or acombination of two or more thereof. The NFC standards covercommunications protocols and data exchange formats, and are based onexisting radio-frequency identification (RFID) standards includingISO/IEC 14443 and FeliCa. The standards include ISO/IEC 18092[3] andthose defined by the NFC Forum.

Additionally, the various aspects of the disclosure may be implementedin a non-generic computer implementation. Moreover, the various aspectsof the disclosure set forth herein improve the functioning of the systemas is apparent from the disclosure hereof. Furthermore, the variousaspects of the disclosure involve computer hardware that it specificallyprogrammed to solve the complex problem addressed by the disclosure.Accordingly, the various aspects of the disclosure improve thefunctioning of the system overall in its specific implementation toperform the process set forth by the disclosure and as defined by theclaims.

In an aspect, the disclosure may be implemented in any type of mobilesmartphones that are operated by any type of advanced mobile dataprocessing and communication operating system, such as, e.g., an AppleiOS operating system, a Google Android operating system, a RIMBlackberry operating system, a Nokia Symbian operating system, aMicrosoft Windows Mobile operating system, a Microsoft Windows Phoneoperating system, a Linux operating system or the like.

Further in accordance with various aspects of the disclosure, themethods described herein are intended for operation with dedicatedhardware implementations including, but not limited to, PCs, PDAs, SIMcards, semiconductors, application specific integrated circuits (ASIC),programmable logic arrays, cloud computing devices, and other hardwaredevices constructed to implement the methods described herein.

While the system and method have been described in terms of what arepresently considered to be specific aspects, the disclosure need not belimited to the disclosed aspects. It is intended to cover variousmodifications and similar arrangements included within the spirit andscope of the claims, the scope of which should be accorded the broadestinterpretation so as to encompass all such modifications and similarstructures. The present disclosure includes any and all aspects of thefollowing claims.

1. A process of sharing a wireless service allotment shared by aplurality of wireless users, the wireless service being provided by athird party wireless network, the process comprising the steps of:implementing a metering system to meter wireless service usage by usersof the third party wireless network; tracking wireless usage by aplurality of wireless devices associated with the metering system;receiving a share request to the metering system from a user device toreallocate the wireless service allotment for at least two of theplurality of wireless devices, the share request being generated by oneof the following: a web portal or a wireless application; determiningwith the metering system whether the share request from the user deviceto reallocate the wireless service allotment for at least two of theplurality of wireless devices is in compliance by comparing the sharerequest to the wireless service allotment remaining for the plurality ofwireless devices; forwarding modification instructions to the meteringsystem when the share request is in compliance; requesting confirmationfrom the metering system that the modification instructions have beenreceived; and modifying the wireless service allotments with themetering system for the at least two of the plurality of wirelessdevices in response to receiving confirmation from the metering system,wherein the metering system is implemented at least in part in anetwork.
 2. The process according to claim 1, wherein the modifying thewireless service allotments comprises modification instructions sent asdata.
 3. The process according to claim 1, wherein the modifying therespective wireless service allotments comprises modificationinstructions sent as non-data.
 4. The process according to claim 1,wherein the metering system is further implemented in at least one ofthe plurality of wireless devices.
 5. The process according to claim 1,wherein the metering system is further implemented at least in part inthe third party wireless network.
 6. The process according to claim 1wherein the metering system is implemented in at least one of theplurality of wireless devices, the third party wireless network, and anetwork.
 7. The process according to claim 1, wherein the receiving ashare request comprises receiving a share request from a one of theplurality of wireless devices.
 8. The process according to claim 1,wherein the receiving a share request comprises receiving a sharerequest from an Internet-based account of one of the plurality ofwireless devices via the web portal.
 9. The process according to claim1, wherein the receiving a share request comprises receiving a sharerequest from the wireless application associated with one of theplurality of wireless devices.
 10. A wireless system configured to sharea wireless service allotment of a plurality of wireless devices, thewireless service allotment being provided by a third party wirelessnetwork comprising: a metering system configured to measure usage ofwireless services of the third party wireless network by the pluralityof wireless devices; the metering system being further configured toreceive a share request from a user device to reallocate the usageallotment for at least two of the plurality of wireless devices, theshare request being generated by one of the following: a web portal or awireless application; the metering system further configured todetermine whether the share request from the user device to reallocatethe wireless service allotment for at least two of the plurality ofwireless devices is in compliance by comparing the share request to thewireless service allotment remaining for the plurality of wirelessdevices; and the metering system being further configured to modify theusage allotments for the at least two of the plurality of wirelessdevices when the share request is in compliance and in response toreceiving confirmation from the at least two of the plurality ofwireless devices, wherein the metering system is implemented at least inpart in a network.
 11. The system according to claim 10, wherein themetering system is configured to modify the respective wireless serviceallotments in response to modification instructions sent as data. 12.The system according to claim 10, wherein the metering system isconfigured to modify the respective wireless service allotments inresponse to modification instructions sent as non-data.
 13. The systemaccording to claim 10, wherein the metering system is furtherimplemented in at least one of the plurality of wireless devices. 14.The system according to claim 10, wherein the metering system is furtherimplemented at least in part in the third party wireless network. 15.The system according to claim 10 wherein the metering system isimplemented in at least one of the plurality of wireless devices, thethird party wireless network, and a network.
 16. The system according toclaim 10, wherein the metering system is configured to receive a sharerequest that comprises receiving a share request from a one of theplurality of wireless devices.
 17. The system according to claim 10,wherein the metering system is configured to receive a share requestthat comprises receiving a share request from an Internet-based accountof one of the plurality of wireless devices via the web portal.
 18. Thesystem according to claim 10, wherein the metering system is configuredto receive a share request that comprises receiving a share request fromthe wireless application associated with one of the plurality ofwireless devices.